EnigmA Amiga Run 1997 July/EnigmA AMIGA RUN 20 (1997)(G.R. Edizioni)(IT)[!][issue 1997-07 & 08][EAR-CD IV].iso/lightwave/lwmlist/95.lightwave-10/001149_owner-lightwav…mail.webcom.com_Thu Oct 19 14:07:38 1995.msg

Internet Message Format | 1995-11-07 | 3KB

Received: by mail.webcom.com
    (1.37.109.15/16.2) id AA189886858; Thu, 19 Oct 1995 14:07:38 -0700
Return-Path: <[e-mail]>
Received: from netcom13.netcom.com by mail.webcom.com with ESMTP
    (1.37.109.15/16.2) id AA189626839; Thu, 19 Oct 1995 14:07:20 -0700
Received: by netcom13.netcom.com (8.6.12/Netcom)
    id NAA27976; Thu, 19 Oct 1995 13:59:09 -0700
Date: Thu, 19 Oct 1995 13:59:06 -0700 (PDT)
From: John Gross <[e-mail]>
Subject: Re: relative paths
To: Ernie Wright <[e-mail]>
Cc: [e-mail]
In-Reply-To: <[e-mail]>
Message-Id: <Pine.3.89.9510191340.A22467-0100000@netcom13>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: [e-mail]
Precedence: bulk



Ernie Wrote:
> > LW writes plug-in filenames in LW.CFG that are relative to the parent
> > of the Programs directory, but won't look there if the Content Directory
> > is pointing somewhere else.  Am I the only person this happens to?
>
> John Gross replied:
>
> > The above behavior sounds very strange.  Every config file I've seen
> > written by LW writes the plug-in lines with full paths.
>
> So I forced myself to track this down today, and here's the deal:  it's
> the Working Directory in my LW icon's properties.  All this time I've
> had it set to D:\NEWTEK.  If I set it to D:\NEWTEK\PROGRAMS, the plug-in
> lines in LW.CFG get written with full paths.  Not only that, but HIIP,
> which had never worked for me at all, suddenly works about as well as it
> does for everyone else, ironically a huge improvement.
>
> The original setting of the working directory came about because I thought
> the .CFG files were supposed to be in D:\NEWTEK, and they are of course
> written to the working directory.  And LW apparently writes plug-in file
> paths that are relative to the working directory, *if* that can be done by
> by simply removing the directory name from the path string.
>
I can see why this is a problem. While beta testing, I originally had all
my content in a Directory called LW, and the LightWave and Modeler
executables were also located there (not in a Programs dir). Everything
worked as it should have, and now that I think about it, the plugin paths
were relative as you stated. It wasn't a problem however, because
LightWave & Modeler were located in the LW dir and that was my working
dir as well.

BTW, On our network, we all run LightWave from one location, but the
working directopry is set to a separate place for each animator, so s/he
can write his own config file. The plugins and HIIP stuff are all full
paths so they work tho...

JG
--
John Gross <[e-mail]> sent this message.
To Post a Message           : [e-mail]
Un/Subscription Requests To : [e-mail]
(DIGEST)                 or : [e-mail]
Administrative Items To     : [e-mail]